Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 239c6dee438541aebe07edb988bba58dd5a2aae5ee021228c501013c7b461c18

Tx prefix hash: e988412896454593bd3f49ca538f53e6c054d40ae906cf587e2c04446636a3fe
Tx public key: fb47cfe9eb0366f0940325e442c473c9e2460bb623db14fafac9a2dc44eb9f12
Timestamp: 1648907435 Timestamp [UCT]: 2022-04-02 13:50:35 Age [y:d:h:m:s]: 03:212:22:46:16
Block: 471678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 930255 RingCT/type: yes/0
Extra: 01fb47cfe9eb0366f0940325e442c473c9e2460bb623db14fafac9a2dc44eb9f120211000000032e6b1fd5000000000000000000

1 output(s) for total of 16.793268437000 dcy

stealth address amount amount idx
00: 07b3fcf1718e37fb4342796e4918659c7cf1d749cfbcbac8c7fdb3d0c41570c0 16.793268437000 891056 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": 471688, "vin": [ { "gen": { "height": 471678 } } ], "vout": [ { "amount": 16793268437, "target": { "key": "07b3fcf1718e37fb4342796e4918659c7cf1d749cfbcbac8c7fdb3d0c41570c0" } } ], "extra": [ 1, 251, 71, 207, 233, 235, 3, 102, 240, 148, 3, 37, 228, 66, 196, 115, 201, 226, 70, 11, 182, 35, 219, 20, 250, 250, 201, 162, 220, 68, 235, 159, 18, 2, 17, 0, 0, 0, 3, 46, 107, 31, 213, 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