Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e31c010374a642ffdbe1049fe009151d2110a38d076d9d3e5cc33a2554489fa8

Tx prefix hash: 263cfa56ec3aac64ed14ed9fb8fab2311909902f8b5bc0a58c7560722266acbd
Tx public key: ef445bf8ae81303a8e5957e6181a5a3fb69e662c160f9db3311b78b3a5a9017b
Timestamp: 1673072861 Timestamp [UCT]: 2023-01-07 06:27:41 Age [y:d:h:m:s]: 02:050:13:44:16
Block: 669358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557808 RingCT/type: yes/0
Extra: 01ef445bf8ae81303a8e5957e6181a5a3fb69e662c160f9db3311b78b3a5a9017b02110000000152542ceb000000000000000000

1 output(s) for total of 3.716541961000 dcy

stealth address amount amount idx
00: 0fbc0211856ffaac59e9b1f8961be7722104c818775d71f733dea1fed0d94495 3.716541961000 1110669 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": 669368, "vin": [ { "gen": { "height": 669358 } } ], "vout": [ { "amount": 3716541961, "target": { "key": "0fbc0211856ffaac59e9b1f8961be7722104c818775d71f733dea1fed0d94495" } } ], "extra": [ 1, 239, 68, 91, 248, 174, 129, 48, 58, 142, 89, 87, 230, 24, 26, 90, 63, 182, 158, 102, 44, 22, 15, 157, 179, 49, 27, 120, 179, 165, 169, 1, 123, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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