Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed049aabbc97a55306e646f755facfd3f2e6061dc19893e618505534e1587f5f

Tx prefix hash: 72a0db0f9316fdbb1b094162f7749910cecce21c304c8720e63a5ed572af323c
Tx public key: cffb7dbee91890bdb070a4a173f2c3e7591713663ababbd75c57d5c404f60d8a
Timestamp: 1702221231 Timestamp [UCT]: 2023-12-10 15:13:51 Age [y:d:h:m:s]: 01:346:07:15:44
Block: 910161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506371 RingCT/type: yes/0
Extra: 01cffb7dbee91890bdb070a4a173f2c3e7591713663ababbd75c57d5c404f60d8a02110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a679b378ce7564c12e12b77a7abdf4f5a75fd8876ae817a5ddbdf9b1893a4d7 0.600000000000 1367306 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": 910171, "vin": [ { "gen": { "height": 910161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a679b378ce7564c12e12b77a7abdf4f5a75fd8876ae817a5ddbdf9b1893a4d7" } } ], "extra": [ 1, 207, 251, 125, 190, 233, 24, 144, 189, 176, 112, 164, 161, 115, 242, 195, 231, 89, 23, 19, 102, 58, 186, 187, 215, 92, 87, 213, 196, 4, 246, 13, 138, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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