Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c8c0daf057ec352833aa808cfb5b9428e3f4fb1e5ab1e57e124a73480f4cb04

Tx prefix hash: 56c205383bd44d109a4d1c6e865f03a7ed0edfbc6594fb03e193b2bddccc64a8
Tx public key: 08214d9c577aa2d8120a6c7bd75b6493a93b18ed3b02b130a3d7793783068541
Timestamp: 1705068333 Timestamp [UCT]: 2024-01-12 14:05:33 Age [y:d:h:m:s]: 01:072:23:40:49
Block: 933757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313255 RingCT/type: yes/0
Extra: 0108214d9c577aa2d8120a6c7bd75b6493a93b18ed3b02b130a3d779378306854102110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ba75f05613701e631550daa6fcde416832cc4857cf54203e93afc4f4bdf14bd 0.600000000000 1391731 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": 933767, "vin": [ { "gen": { "height": 933757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ba75f05613701e631550daa6fcde416832cc4857cf54203e93afc4f4bdf14bd" } } ], "extra": [ 1, 8, 33, 77, 156, 87, 122, 162, 216, 18, 10, 108, 123, 215, 91, 100, 147, 169, 59, 24, 237, 59, 2, 177, 48, 163, 215, 121, 55, 131, 6, 133, 65, 2, 17, 0, 0, 0, 3, 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