Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6732418a9ef342be2b1fd251a1e891546571c200923e7d5d7cced7f72606d298

Tx prefix hash: f81a0b090a8fe603cf597b1f7f8217e5d3c4c97d572a2aa172b5df81e3295c35
Tx public key: aa2ae33ae9087f78d24e7645b0c6e31d9d01a6cebc0956f89f90614136cdeec1
Timestamp: 1704519587 Timestamp [UCT]: 2024-01-06 05:39:47 Age [y:d:h:m:s]: 01:308:16:00:20
Block: 929192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479444 RingCT/type: yes/0
Extra: 01aa2ae33ae9087f78d24e7645b0c6e31d9d01a6cebc0956f89f90614136cdeec102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14db9c08d8d5e5bde1afa0a6a23d9a701b574beb4b4fe805ede8d2928950ddb9 0.600000000000 1387060 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": 929202, "vin": [ { "gen": { "height": 929192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14db9c08d8d5e5bde1afa0a6a23d9a701b574beb4b4fe805ede8d2928950ddb9" } } ], "extra": [ 1, 170, 42, 227, 58, 233, 8, 127, 120, 210, 78, 118, 69, 176, 198, 227, 29, 157, 1, 166, 206, 188, 9, 86, 248, 159, 144, 97, 65, 54, 205, 238, 193, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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