Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c587c99cd96128aa2122552ab072a9b09221083b8d4f0742afd77be473b76f9b

Tx prefix hash: cfa2b86741e4f5d2305c966b66b622037004d06e27ced8d5df66e8f302406b04
Tx public key: 469b0f23c349b6b6bd6d52674a94650a882b66f9f997743b65443c42ca3e4076
Timestamp: 1739809701 Timestamp [UCT]: 2025-02-17 16:28:21 Age [y:d:h:m:s]: 00:274:21:46:30
Block: 1221323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194248 RingCT/type: yes/0
Extra: 01469b0f23c349b6b6bd6d52674a94650a882b66f9f997743b65443c42ca3e407602110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5755151d4fc9cf859bea3331fbfa6ab9ee860341c837d8de8b866c393c512ab 0.600000000000 1708168 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": 1221333, "vin": [ { "gen": { "height": 1221323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5755151d4fc9cf859bea3331fbfa6ab9ee860341c837d8de8b866c393c512ab" } } ], "extra": [ 1, 70, 155, 15, 35, 195, 73, 182, 182, 189, 109, 82, 103, 74, 148, 101, 10, 136, 43, 102, 249, 249, 151, 116, 59, 101, 68, 60, 66, 202, 62, 64, 118, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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