Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03100b5e085a3aef9cb1e107ffb9924c7d532ed9f943859ea9bf8dd124578875

Tx prefix hash: 8a1cb9e75e94fdefb4421995cd2579507566cddea43a7b1bd8cb7a85af6b5e23
Tx public key: 2cfa45525f802c49e81557d28dfb55c8e66edbcdb83ec2037adf127703b4e572
Timestamp: 1652833767 Timestamp [UCT]: 2022-05-18 00:29:27 Age [y:d:h:m:s]: 02:305:07:16:19
Block: 503240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738590 RingCT/type: yes/0
Extra: 012cfa45525f802c49e81557d28dfb55c8e66edbcdb83ec2037adf127703b4e572021100000010cb8520c2000000000000000000

1 output(s) for total of 13.199490748000 dcy

stealth address amount amount idx
00: 01510067c0227b5eb9c525310ed203f59f809ee3f0045b240166023c98ff3313 13.199490748000 928279 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": 503250, "vin": [ { "gen": { "height": 503240 } } ], "vout": [ { "amount": 13199490748, "target": { "key": "01510067c0227b5eb9c525310ed203f59f809ee3f0045b240166023c98ff3313" } } ], "extra": [ 1, 44, 250, 69, 82, 95, 128, 44, 73, 232, 21, 87, 210, 141, 251, 85, 200, 230, 110, 219, 205, 184, 62, 194, 3, 122, 223, 18, 119, 3, 180, 229, 114, 2, 17, 0, 0, 0, 16, 203, 133, 32, 194, 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