Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5231d5f5bc4830af16615768d8f902e894624f5ef90ccc710bd0c381a51c2d4

Tx prefix hash: 01938c578a4f936d4d8856b55c08e698cefcba1090970fd8e074fd2836face0c
Tx public key: 87b5419e0bf22f7a1a799267e91848effaa1d9e7fc820dc17f431a4892949e03
Timestamp: 1704296861 Timestamp [UCT]: 2024-01-03 15:47:41 Age [y:d:h:m:s]: 01:311:00:46:16
Block: 927385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481107 RingCT/type: yes/0
Extra: 0187b5419e0bf22f7a1a799267e91848effaa1d9e7fc820dc17f431a4892949e030211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dabb5bb05b95a032f3db97b2a52c27b8f7678678ed23bf79e5d695ee5aafbdc8 0.600000000000 1385221 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": 927395, "vin": [ { "gen": { "height": 927385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dabb5bb05b95a032f3db97b2a52c27b8f7678678ed23bf79e5d695ee5aafbdc8" } } ], "extra": [ 1, 135, 181, 65, 158, 11, 242, 47, 122, 26, 121, 146, 103, 233, 24, 72, 239, 250, 161, 217, 231, 252, 130, 13, 193, 127, 67, 26, 72, 146, 148, 158, 3, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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