Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1753da3652a441c7c90da11264d2dcd93fe4a250b3a93a2fcc25fb918f62aa4f

Tx prefix hash: 02df0ce4bf826157cfb517bd84e8c972d4179c0dbd9d80d44d45c9238b879035
Tx public key: 0ee7936021fac0fdb7b10a3e706be45b99e057da24187d5b5fe63c78a1157025
Timestamp: 1677926600 Timestamp [UCT]: 2023-03-04 10:43:20 Age [y:d:h:m:s]: 02:045:11:20:35
Block: 709634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554062 RingCT/type: yes/0
Extra: 010ee7936021fac0fdb7b10a3e706be45b99e057da24187d5b5fe63c78a11570250211000000015029cbac000000000000000000

1 output(s) for total of 2.733303605000 dcy

stealth address amount amount idx
00: f6bf0eecce157d6fea9c6863a7b2d9e804ec445f7a97c26210c06379cd7d1091 2.733303605000 1153639 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": 709644, "vin": [ { "gen": { "height": 709634 } } ], "vout": [ { "amount": 2733303605, "target": { "key": "f6bf0eecce157d6fea9c6863a7b2d9e804ec445f7a97c26210c06379cd7d1091" } } ], "extra": [ 1, 14, 231, 147, 96, 33, 250, 192, 253, 183, 177, 10, 62, 112, 107, 228, 91, 153, 224, 87, 218, 36, 24, 125, 91, 95, 230, 60, 120, 161, 21, 112, 37, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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