Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 682359df45e542b9ccd4de0be576fef80e72c495d8e3dbd7a998b0e173601be1

Tx prefix hash: 45b22b2d2a24a527e9082ddae265534c3faf42c761f81a5fe7e449eba1f8992d
Tx public key: 085117c1a9ac619bbd8b1a74b4bf8fe0049fed4932625853e442a862540e244a
Timestamp: 1717210650 Timestamp [UCT]: 2024-06-01 02:57:30 Age [y:d:h:m:s]: 00:288:08:06:38
Block: 1034434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206073 RingCT/type: yes/0
Extra: 01085117c1a9ac619bbd8b1a74b4bf8fe0049fed4932625853e442a862540e244a02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2770ba73c2978e064f662625912b72dec0a8c6143c73fcc0856f2b2b216ad494 0.600000000000 1502947 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": 1034444, "vin": [ { "gen": { "height": 1034434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2770ba73c2978e064f662625912b72dec0a8c6143c73fcc0856f2b2b216ad494" } } ], "extra": [ 1, 8, 81, 23, 193, 169, 172, 97, 155, 189, 139, 26, 116, 180, 191, 143, 224, 4, 159, 237, 73, 50, 98, 88, 83, 228, 66, 168, 98, 84, 14, 36, 74, 2, 17, 0, 0, 0, 7, 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