Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6d0e7de7d21d3b9863f6804c86b3bd19706a29d5878f38442a97c71ee36b95

Tx prefix hash: 8d46fb2cfcc845326b15a8acd3bf9f48f1afd40284b0ccf7b14f5863f38b2859
Tx public key: 57498e025559596e64d9717951a6fd2e0890378d5d1745ebe4b897505a303367
Timestamp: 1714415077 Timestamp [UCT]: 2024-04-29 18:24:37 Age [y:d:h:m:s]: 01:192:15:54:12
Block: 1011245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396340 RingCT/type: yes/0
Extra: 0157498e025559596e64d9717951a6fd2e0890378d5d1745ebe4b897505a30336702110000000252d47e94000000000000000000

1 output(s) for total of 0.619640000000 dcy

stealth address amount amount idx
00: 3a948620d4ac9f7bc8895d3ca30d25d72e44b62dbef80f5dd956a915177d0f19 0.619640000000 1473423 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": 1011255, "vin": [ { "gen": { "height": 1011245 } } ], "vout": [ { "amount": 619640000, "target": { "key": "3a948620d4ac9f7bc8895d3ca30d25d72e44b62dbef80f5dd956a915177d0f19" } } ], "extra": [ 1, 87, 73, 142, 2, 85, 89, 89, 110, 100, 217, 113, 121, 81, 166, 253, 46, 8, 144, 55, 141, 93, 23, 69, 235, 228, 184, 151, 80, 90, 48, 51, 103, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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