Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d455a58aa1efede849e8a2ae785abd046e86716f12f1a010e3b994335ec8a8cc

Tx prefix hash: 1240e0b41e809495020f6b6d4f59114073dd2a5d757e12f6a57bdac3805c711a
Tx public key: 24e260bcc36670cbf8d41f6320a42029e8209f4a2b04fc443b76384682a1a8ff
Timestamp: 1721927283 Timestamp [UCT]: 2024-07-25 17:08:03 Age [y:d:h:m:s]: 00:242:02:04:22
Block: 1073527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172925 RingCT/type: yes/0
Extra: 0124e260bcc36670cbf8d41f6320a42029e8209f4a2b04fc443b76384682a1a8ff02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4d02c35b137499fcd7cb711e1e9eef558f8249ea72459aa792e01858cc54a6c 0.600000000000 1546030 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": 1073537, "vin": [ { "gen": { "height": 1073527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4d02c35b137499fcd7cb711e1e9eef558f8249ea72459aa792e01858cc54a6c" } } ], "extra": [ 1, 36, 226, 96, 188, 195, 102, 112, 203, 248, 212, 31, 99, 32, 164, 32, 41, 232, 32, 159, 74, 43, 4, 252, 68, 59, 118, 56, 70, 130, 161, 168, 255, 2, 17, 0, 0, 0, 10, 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