Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31edbdde4c5129d2e889a44dbf74011cf983ef0b601b9b9c6cbb4164047657dd

Tx prefix hash: 146990ffd4fee577659b87d435e95126d672e3d85cf2f3e421cc2f174fbd8e58
Tx public key: bc7789fdaa6e6d2f5f06f3458b430957418602fa9e8896b75536bcb4dc423f65
Timestamp: 1682596433 Timestamp [UCT]: 2023-04-27 11:53:53 Age [y:d:h:m:s]: 01:342:04:18:07
Block: 747713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505806 RingCT/type: yes/0
Extra: 01bc7789fdaa6e6d2f5f06f3458b430957418602fa9e8896b75536bcb4dc423f650211000000017e406890000000000000000000

1 output(s) for total of 2.044168290000 dcy

stealth address amount amount idx
00: f29748aeedb7ae911a8f375fac79f2dcac6f7c062e8ec61261e70df9d0731641 2.044168290000 1195456 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": 747723, "vin": [ { "gen": { "height": 747713 } } ], "vout": [ { "amount": 2044168290, "target": { "key": "f29748aeedb7ae911a8f375fac79f2dcac6f7c062e8ec61261e70df9d0731641" } } ], "extra": [ 1, 188, 119, 137, 253, 170, 110, 109, 47, 95, 6, 243, 69, 139, 67, 9, 87, 65, 134, 2, 250, 158, 136, 150, 183, 85, 54, 188, 180, 220, 66, 63, 101, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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