Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1987e0dd3c1cfc2d14210d3fd62e6e24063c2009f74b9c67ad663a0163b59e

Tx prefix hash: 780e35b2ad95bb2681af6fda5b434852221f74a66bce6d23d18cd62327599780
Tx public key: 4d0ef8fdc3678be66fbe6106635b325d9aacabb0634eaeaa933d0fc70dbe3e4a
Timestamp: 1713607261 Timestamp [UCT]: 2024-04-20 10:01:01 Age [y:d:h:m:s]: 00:218:17:29:46
Block: 1004539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156596 RingCT/type: yes/0
Extra: 014d0ef8fdc3678be66fbe6106635b325d9aacabb0634eaeaa933d0fc70dbe3e4a02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73cb1ed12829d6eba2ac5c9e1d72dd4a6d3b4f51bdc44f8ebf7b8de854fdee2c 0.600000000000 1465107 of 15

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": 1004549, "vin": [ { "gen": { "height": 1004539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73cb1ed12829d6eba2ac5c9e1d72dd4a6d3b4f51bdc44f8ebf7b8de854fdee2c" } } ], "extra": [ 1, 77, 14, 248, 253, 195, 103, 139, 230, 111, 190, 97, 6, 99, 91, 50, 93, 154, 172, 171, 176, 99, 78, 174, 170, 147, 61, 15, 199, 13, 190, 62, 74, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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