Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44f73747f695cfce174815efc0d9bb4a7d6a98cfe108f1497208f13787a6fb9

Tx prefix hash: 9d17920a3e87e384c731f77430e036debd00ccb34f7af8511f9b10d4980a83e2
Tx public key: dc161396630a3e4ffce0c4407b59aeaf13de77449c2f6a79aacf329d6dd1946d
Timestamp: 1721519245 Timestamp [UCT]: 2024-07-20 23:47:25 Age [y:d:h:m:s]: 00:190:19:25:57
Block: 1070149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136277 RingCT/type: yes/0
Extra: 01dc161396630a3e4ffce0c4407b59aeaf13de77449c2f6a79aacf329d6dd1946d02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5950d64bc40aced6334967ff25eb96648b2e0db3f85f29a32a5f1f854c99a9f 0.600000000000 1541860 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": 1070159, "vin": [ { "gen": { "height": 1070149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5950d64bc40aced6334967ff25eb96648b2e0db3f85f29a32a5f1f854c99a9f" } } ], "extra": [ 1, 220, 22, 19, 150, 99, 10, 62, 79, 252, 224, 196, 64, 123, 89, 174, 175, 19, 222, 119, 68, 156, 47, 106, 121, 170, 207, 50, 157, 109, 209, 148, 109, 2, 17, 0, 0, 0, 13, 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