Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e30a1b51c493f51caf28c46dec169880c6efe37d7b0f126107a76d867bba94e

Tx prefix hash: aab70426973b61784e42c55f863ea6e35f26f73ea40d3ff987261ca20ade31f4
Tx public key: ba3b202a7ff7978f517e4db8547ef07af850a5371d5b9f3dd65039aae8c30dea
Timestamp: 1673930681 Timestamp [UCT]: 2023-01-17 04:44:41 Age [y:d:h:m:s]: 01:303:09:02:01
Block: 676476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477803 RingCT/type: yes/0
Extra: 01ba3b202a7ff7978f517e4db8547ef07af850a5371d5b9f3dd65039aae8c30dea0211000000058b7b6602000000000000000000

1 output(s) for total of 3.520093029000 dcy

stealth address amount amount idx
00: 51174061ab1a8ddbb64ddb040f7b2f918b779370ad2637be0f23b1c2e4d058d6 3.520093029000 1118193 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": 676486, "vin": [ { "gen": { "height": 676476 } } ], "vout": [ { "amount": 3520093029, "target": { "key": "51174061ab1a8ddbb64ddb040f7b2f918b779370ad2637be0f23b1c2e4d058d6" } } ], "extra": [ 1, 186, 59, 32, 42, 127, 247, 151, 143, 81, 126, 77, 184, 84, 126, 240, 122, 248, 80, 165, 55, 29, 91, 159, 61, 214, 80, 57, 170, 232, 195, 13, 234, 2, 17, 0, 0, 0, 5, 139, 123, 102, 2, 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