Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7e781ea5953c87b70f4f1c46e780b3a926c4ebf85aeafbf36f3ff8e984e00a3

Tx prefix hash: 0ea815bea0d9747c5904e34e830980f054d8cf68db5ecd2fa7c36d0655da606a
Tx public key: ec532c9ffabff52342cc5eefcffc088644c8305971c8cc86a0dcea020f2900e0
Timestamp: 1681933654 Timestamp [UCT]: 2023-04-19 19:47:34 Age [y:d:h:m:s]: 01:312:22:22:26
Block: 742208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484895 RingCT/type: yes/0
Extra: 01ec532c9ffabff52342cc5eefcffc088644c8305971c8cc86a0dcea020f2900e002110000000275e3f0e9000000000000000000

1 output(s) for total of 2.131851775000 dcy

stealth address amount amount idx
00: b2856a84ad2e70bf356983dd23330c14f3e967627bbead731044cd427ede10f9 2.131851775000 1189167 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": 742218, "vin": [ { "gen": { "height": 742208 } } ], "vout": [ { "amount": 2131851775, "target": { "key": "b2856a84ad2e70bf356983dd23330c14f3e967627bbead731044cd427ede10f9" } } ], "extra": [ 1, 236, 83, 44, 159, 250, 191, 245, 35, 66, 204, 94, 239, 207, 252, 8, 134, 68, 200, 48, 89, 113, 200, 204, 134, 160, 220, 234, 2, 15, 41, 0, 224, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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