Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9fe4476ffd28915362362054b1cb31ee929e11a48982e16a3d0146f0e753dae1

Tx prefix hash: f82e22452ce2a301108d4b1402baf5a4e7931062bee907397ad64a0f33856d99
Tx public key: e534d8f7627d359595563fcef1069c03b9a69150b0339a7113afa0ebcdcf1e1d
Timestamp: 1647475053 Timestamp [UCT]: 2022-03-16 23:57:33 Age [y:d:h:m:s]: 02:282:02:00:30
Block: 459995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721160 RingCT/type: yes/0
Extra: 01e534d8f7627d359595563fcef1069c03b9a69150b0339a7113afa0ebcdcf1e1d0211000000052e6b1fd5000000000000000000

1 output(s) for total of 18.358867021000 dcy

stealth address amount amount idx
00: 285252fb071a96372b22a85f5a539481a98a799a5dfdd36048b5e0f5c86f8cb9 18.358867021000 876876 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 460005, "vin": [ { "gen": { "height": 459995 } } ], "vout": [ { "amount": 18358867021, "target": { "key": "285252fb071a96372b22a85f5a539481a98a799a5dfdd36048b5e0f5c86f8cb9" } } ], "extra": [ 1, 229, 52, 216, 247, 98, 125, 53, 149, 149, 86, 63, 206, 241, 6, 156, 3, 185, 166, 145, 80, 176, 51, 154, 113, 19, 175, 160, 235, 205, 207, 30, 29, 2, 17, 0, 0, 0, 5, 46, 107, 31, 213, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8