Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb3684a37124dabbd0af43b5023fe7682ecdc04c96be76f31d64132c099415eb

Tx prefix hash: 010153b4d08e677388a647a9e824897749be8c2e8dac6fdd2fffd8bb22ac67e6
Tx public key: 950d9e81be8af94f381297f8cba4d10a7e8d80fda60c3c22ce7b337e380d76da
Timestamp: 1673538320 Timestamp [UCT]: 2023-01-12 15:45:20 Age [y:d:h:m:s]: 02:087:15:09:56
Block: 673229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584303 RingCT/type: yes/0
Extra: 01950d9e81be8af94f381297f8cba4d10a7e8d80fda60c3c22ce7b337e380d76da0211000000038b7b6602000000000000000000

1 output(s) for total of 3.608384469000 dcy

stealth address amount amount idx
00: 2cffce4e6c77e41b1b9bb3f7839c3788187bf5268e051af706d0c377edd6c1f3 3.608384469000 1114826 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": 673239, "vin": [ { "gen": { "height": 673229 } } ], "vout": [ { "amount": 3608384469, "target": { "key": "2cffce4e6c77e41b1b9bb3f7839c3788187bf5268e051af706d0c377edd6c1f3" } } ], "extra": [ 1, 149, 13, 158, 129, 190, 138, 249, 79, 56, 18, 151, 248, 203, 164, 209, 10, 126, 141, 128, 253, 166, 12, 60, 34, 206, 123, 51, 126, 56, 13, 118, 218, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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