Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81f2a77e0a1ce74237b4a87cd51a7aa0994bcc55aff2082dfbb3be58a9a84200

Tx prefix hash: 449f0899b2283eb4a044cb13d725fc782ecc4a65e7c7d59238200be4a151a003
Tx public key: 2f0d2e56e170cf253551072c47e09856b55f92b1f18fa918f934447edc36d386
Timestamp: 1730154741 Timestamp [UCT]: 2024-10-28 22:32:21 Age [y:d:h:m:s]: 00:149:04:30:58
Block: 1141673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106430 RingCT/type: yes/0
Extra: 012f0d2e56e170cf253551072c47e09856b55f92b1f18fa918f934447edc36d3860211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a9aa906f8b57335ae362094bc8bdf89826c6ad0aa1d1160e326457e536fe5e3 0.600000000000 1625484 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": 1141683, "vin": [ { "gen": { "height": 1141673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a9aa906f8b57335ae362094bc8bdf89826c6ad0aa1d1160e326457e536fe5e3" } } ], "extra": [ 1, 47, 13, 46, 86, 225, 112, 207, 37, 53, 81, 7, 44, 71, 224, 152, 86, 181, 95, 146, 177, 241, 143, 169, 24, 249, 52, 68, 126, 220, 54, 211, 134, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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