Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 486181bbd31f739089d6755b63329bcdc6c422f3ba73e04a60600383559f2f41

Tx prefix hash: 872f974ca69ff45b9c8a7bc75e094de85c4ea415699f94aab46979570abd2c76
Tx public key: c93bdddefe44e8781ac5d2c3e88c55ef5c0cf8f811c3bb353228dab1ead5290c
Timestamp: 1706496092 Timestamp [UCT]: 2024-01-29 02:41:32 Age [y:d:h:m:s]: 01:071:19:55:12
Block: 945577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312421 RingCT/type: yes/0
Extra: 01c93bdddefe44e8781ac5d2c3e88c55ef5c0cf8f811c3bb353228dab1ead5290c02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 112e9a0c982eff9fd00b8ed0b0994ca4a2d79ca03cfdfff195a08cee860ab1d6 0.600000000000 1403893 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": 945587, "vin": [ { "gen": { "height": 945577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "112e9a0c982eff9fd00b8ed0b0994ca4a2d79ca03cfdfff195a08cee860ab1d6" } } ], "extra": [ 1, 201, 59, 221, 222, 254, 68, 232, 120, 26, 197, 210, 195, 232, 140, 85, 239, 92, 12, 248, 248, 17, 195, 187, 53, 50, 40, 218, 177, 234, 213, 41, 12, 2, 17, 0, 0, 0, 7, 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