Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ca19b217bbd8bff7a14afc77acc5ee7f23095c016c3377b79ad5ac423f1d07b

Tx prefix hash: b0d36a63ad7d70e506fb65019ed3e60ff70622bc366591e60a70049cd339dffc
Tx public key: 7172ec7f1fd5af127b0f0cd70085e8c6fd6dbbb841d3385b3dadd4532ab89771
Timestamp: 1724849250 Timestamp [UCT]: 2024-08-28 12:47:30 Age [y:d:h:m:s]: 00:134:12:46:09
Block: 1097751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96234 RingCT/type: yes/0
Extra: 017172ec7f1fd5af127b0f0cd70085e8c6fd6dbbb841d3385b3dadd4532ab8977102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90cc7fbaf5d1e3ec648a2487ece05765b4420d5708678be0c9dc0e7e85811a5e 0.600000000000 1573230 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": 1097761, "vin": [ { "gen": { "height": 1097751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90cc7fbaf5d1e3ec648a2487ece05765b4420d5708678be0c9dc0e7e85811a5e" } } ], "extra": [ 1, 113, 114, 236, 127, 31, 213, 175, 18, 123, 15, 12, 215, 0, 133, 232, 198, 253, 109, 187, 184, 65, 211, 56, 91, 61, 173, 212, 83, 42, 184, 151, 113, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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