Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29174ace0cf949305cf6926b1b527eff0f9b85c3cc00b52bf0d62c73e694baf1

Tx prefix hash: b9d640d3d554c8925ec2ae084f8a4688825fc3521a652fe0c7a9d716361428a6
Tx public key: a3ea06d742b334717ee33163428927f3da5fb97f1b7fbaa91595f5be46589017
Timestamp: 1737490232 Timestamp [UCT]: 2025-01-21 20:10:32 Age [y:d:h:m:s]: 00:148:17:10:32
Block: 1202358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106032 RingCT/type: yes/0
Extra: 01a3ea06d742b334717ee33163428927f3da5fb97f1b7fbaa91595f5be4658901702110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b108d05c9dda50b3b57c2ff00a224c6db2ef50a1b61a6e1f757f8092a1c5882a 0.600000000000 1689021 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": 1202368, "vin": [ { "gen": { "height": 1202358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b108d05c9dda50b3b57c2ff00a224c6db2ef50a1b61a6e1f757f8092a1c5882a" } } ], "extra": [ 1, 163, 234, 6, 215, 66, 179, 52, 113, 126, 227, 49, 99, 66, 137, 39, 243, 218, 95, 185, 127, 27, 127, 186, 169, 21, 149, 245, 190, 70, 88, 144, 23, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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