Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3899566a402e4a0f0a4567321fb367e62627bd98c472f4e1dcb2fd4d1e0c5bf5

Tx prefix hash: 3e7a2a8ec9d67f01455af976eaa53ac002210753e467a5da2401d8dbbc7a2ffa
Tx public key: e2b5f80a19c1a6438d65dc21958f875dfb9ee57ce15e4fd77444d98d49df8b4e
Timestamp: 1711057127 Timestamp [UCT]: 2024-03-21 21:38:47 Age [y:d:h:m:s]: 00:363:00:31:50
Block: 983439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259556 RingCT/type: yes/0
Extra: 01e2b5f80a19c1a6438d65dc21958f875dfb9ee57ce15e4fd77444d98d49df8b4e02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66a0fac20142b7afb78d56224fbd3c173941d6c1344a7b107e89915200343454 0.600000000000 1443570 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": 983449, "vin": [ { "gen": { "height": 983439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66a0fac20142b7afb78d56224fbd3c173941d6c1344a7b107e89915200343454" } } ], "extra": [ 1, 226, 181, 248, 10, 25, 193, 166, 67, 141, 101, 220, 33, 149, 143, 135, 93, 251, 158, 229, 124, 225, 94, 79, 215, 116, 68, 217, 141, 73, 223, 139, 78, 2, 17, 0, 0, 0, 6, 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