Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efd37c0fe9577e02b630e7719c27d4b049ec6f2107b03ecb1043a5be9e8062c3

Tx prefix hash: d220db70d0b0f447b7728e30c15045a8308edd8a6b148f6999f77a534a8393a1
Tx public key: c4a07eb4fcfee75c39d32a60a9569bfbb3e9ce638214399063027fa43eb4f49f
Timestamp: 1686115171 Timestamp [UCT]: 2023-06-07 05:19:31 Age [y:d:h:m:s]: 01:271:21:09:58
Block: 776878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455496 RingCT/type: yes/0
Extra: 01c4a07eb4fcfee75c39d32a60a9569bfbb3e9ce638214399063027fa43eb4f49f021100000002faf35c9c000000000000000000

1 output(s) for total of 1.636367526000 dcy

stealth address amount amount idx
00: 1cba01f7ed6c05a007dbb8509381bf4e8925294c1f201ef04f4c02c21590f395 1.636367526000 1226445 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": 776888, "vin": [ { "gen": { "height": 776878 } } ], "vout": [ { "amount": 1636367526, "target": { "key": "1cba01f7ed6c05a007dbb8509381bf4e8925294c1f201ef04f4c02c21590f395" } } ], "extra": [ 1, 196, 160, 126, 180, 252, 254, 231, 92, 57, 211, 42, 96, 169, 86, 155, 251, 179, 233, 206, 99, 130, 20, 57, 144, 99, 2, 127, 164, 62, 180, 244, 159, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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