Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adb20c6e1d707ae11c7ea01e91693f0ace35cbf86ee367505ba510ae3dfd7e00

Tx prefix hash: 4711e0f370e15a4f5808ff24cb55608c452db33017eebf5854357fac1ebc9c3e
Tx public key: 2992bccfc22666fdf1cb9c8a87d540b039d9e5e15dfd7db144a5f7e7fda085d4
Timestamp: 1699508245 Timestamp [UCT]: 2023-11-09 05:37:25 Age [y:d:h:m:s]: 01:153:08:48:12
Block: 887672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370801 RingCT/type: yes/0
Extra: 012992bccfc22666fdf1cb9c8a87d540b039d9e5e15dfd7db144a5f7e7fda085d4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.702706831000 dcy

stealth address amount amount idx
00: 35e9a6ff6014cab89be7ed8126281350909a48fedbd73414e098521dfac5c84a 0.702706831000 1343565 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": 887682, "vin": [ { "gen": { "height": 887672 } } ], "vout": [ { "amount": 702706831, "target": { "key": "35e9a6ff6014cab89be7ed8126281350909a48fedbd73414e098521dfac5c84a" } } ], "extra": [ 1, 41, 146, 188, 207, 194, 38, 102, 253, 241, 203, 156, 138, 135, 213, 64, 176, 57, 217, 229, 225, 93, 253, 125, 177, 68, 165, 247, 231, 253, 160, 133, 212, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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