Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a341f9819e1ec5ca07c1c85d317782d2e003faeb3bc9a1d67eb17242510085e

Tx prefix hash: c36d116e7703d0dac5d45480840875bd27dc999393e15699626798a7bf9a45a3
Tx public key: df2be123d02a56d980edfe3730932b120745ac3d413dc85549b8a062483af2a3
Timestamp: 1577931145 Timestamp [UCT]: 2020-01-02 02:12:25 Age [y:d:h:m:s]: 04:359:04:04:52
Block: 36831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145861 RingCT/type: yes/0
Extra: 01df2be123d02a56d980edfe3730932b120745ac3d413dc85549b8a062483af2a3021100000006d81c26c0000000000000000000

1 output(s) for total of 463.408995632000 dcy

stealth address amount amount idx
00: 2aba634ff6d9d77f0a89d4b826a27814841cef9a3fa4ed0f2db5d3e748084aa3 463.408995632000 62443 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": 36841, "vin": [ { "gen": { "height": 36831 } } ], "vout": [ { "amount": 463408995632, "target": { "key": "2aba634ff6d9d77f0a89d4b826a27814841cef9a3fa4ed0f2db5d3e748084aa3" } } ], "extra": [ 1, 223, 43, 225, 35, 208, 42, 86, 217, 128, 237, 254, 55, 48, 147, 43, 18, 7, 69, 172, 61, 65, 61, 200, 85, 73, 184, 160, 98, 72, 58, 242, 163, 2, 17, 0, 0, 0, 6, 216, 28, 38, 192, 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