Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c80b3c298bd860c525d352f87e2b7cbc5f9d5767edc66bfe25ce519a2c785d0b

Tx prefix hash: b43fd008cee976240d2ce3e70a7c8c1f15cb0298d77c8caba29f6fd2b9a25397
Tx public key: 9b55c887faeb0529619b2e2a7d0efc5275f8b7dff967afea07d33a1dcaf61e2a
Timestamp: 1715088707 Timestamp [UCT]: 2024-05-07 13:31:47 Age [y:d:h:m:s]: 00:354:13:41:08
Block: 1016848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253458 RingCT/type: yes/0
Extra: 019b55c887faeb0529619b2e2a7d0efc5275f8b7dff967afea07d33a1dcaf61e2a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdcbc5f2d069b0af9f518e483c3bcee565f4035e8fab59e8960342e313935d73 0.600000000000 1480553 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": 1016858, "vin": [ { "gen": { "height": 1016848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdcbc5f2d069b0af9f518e483c3bcee565f4035e8fab59e8960342e313935d73" } } ], "extra": [ 1, 155, 85, 200, 135, 250, 235, 5, 41, 97, 155, 46, 42, 125, 14, 252, 82, 117, 248, 183, 223, 249, 103, 175, 234, 7, 211, 58, 29, 202, 246, 30, 42, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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