Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f14cc7ef006972af4e7c279999a0376f0109111126cd0b1230d59de7a9bee11

Tx prefix hash: ae2428573d0c3a2fb462949ec2b4d2c934da56896ab185e7b7c0d3d23e49781f
Tx public key: f3a437e707167a104aaf1fc4e3e8b6609332b19facd4facc314822ab6e9d2ae6
Timestamp: 1706690193 Timestamp [UCT]: 2024-01-31 08:36:33 Age [y:d:h:m:s]: 01:280:23:39:08
Block: 947191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459617 RingCT/type: yes/0
Extra: 01f3a437e707167a104aaf1fc4e3e8b6609332b19facd4facc314822ab6e9d2ae602110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 649466efe4b0cea2a7ebcdbb7fb444a2ec4d8f3e8f70b56bbfcb63ade6605cf2 0.600000000000 1405539 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": 947201, "vin": [ { "gen": { "height": 947191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "649466efe4b0cea2a7ebcdbb7fb444a2ec4d8f3e8f70b56bbfcb63ade6605cf2" } } ], "extra": [ 1, 243, 164, 55, 231, 7, 22, 122, 16, 74, 175, 31, 196, 227, 232, 182, 96, 147, 50, 177, 159, 172, 212, 250, 204, 49, 72, 34, 171, 110, 157, 42, 230, 2, 17, 0, 0, 0, 4, 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