Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39697d7ec2e1054fd59123b1a0bacbca01a043a9783990e86791bc805bc0e196

Tx prefix hash: 48efb776aec150f093dfde6a191c0d703dcf888cb3a506aae427a3a0f87dfd7e
Tx public key: fb874e0704697d8bc3dd62e4bb419af8fa432c458f4cdd297518293726269175
Timestamp: 1704848020 Timestamp [UCT]: 2024-01-10 00:53:40 Age [y:d:h:m:s]: 01:081:12:54:57
Block: 931926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319371 RingCT/type: yes/0
Extra: 01fb874e0704697d8bc3dd62e4bb419af8fa432c458f4cdd29751829372626917502110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc28a16e7f2351f57e1a3a9fa95ee4bb7724f45ee4b770d0ac72bbd77fab3478 0.600000000000 1389834 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": 931936, "vin": [ { "gen": { "height": 931926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc28a16e7f2351f57e1a3a9fa95ee4bb7724f45ee4b770d0ac72bbd77fab3478" } } ], "extra": [ 1, 251, 135, 78, 7, 4, 105, 125, 139, 195, 221, 98, 228, 187, 65, 154, 248, 250, 67, 44, 69, 143, 76, 221, 41, 117, 24, 41, 55, 38, 38, 145, 117, 2, 17, 0, 0, 0, 5, 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