Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4877264d77edee02fe715875c6e9e415c0937b44c5cb34cbc91a8cae4cd05c2b

Tx prefix hash: 0d25b6ab0bda8af1e9f4586700774126670b100178757dc1872e2330431c911c
Tx public key: 7d08ee45baa9eb581442ceaf4e5c1580dcaa34fde65e4374bcece4e0f16af82e
Timestamp: 1718963971 Timestamp [UCT]: 2024-06-21 09:59:31 Age [y:d:h:m:s]: 01:140:11:36:50
Block: 1048942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358977 RingCT/type: yes/0
Extra: 017d08ee45baa9eb581442ceaf4e5c1580dcaa34fde65e4374bcece4e0f16af82e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35fcef2c4b9f2512d6ec2449f926b1c4ef9e0ad66b6eab5429549e1e30eb47f8 0.600000000000 1519037 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": 1048952, "vin": [ { "gen": { "height": 1048942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35fcef2c4b9f2512d6ec2449f926b1c4ef9e0ad66b6eab5429549e1e30eb47f8" } } ], "extra": [ 1, 125, 8, 238, 69, 186, 169, 235, 88, 20, 66, 206, 175, 78, 92, 21, 128, 220, 170, 52, 253, 230, 94, 67, 116, 188, 236, 228, 224, 241, 106, 248, 46, 2, 17, 0, 0, 0, 3, 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