Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b23e4f5353dc61ca98487253f3b3a43816118800d5bedc9b5d02a824b79db4f0

Tx prefix hash: 2304e1ccea2d3c6d52360f46db25172c5ab5cc4736fbc75b16d2cc8e8f1db89d
Tx public key: 399c091a5f850afc13740303f2f14ebeef2ddd4db3e95a4c9d0041c7dfd0049d
Timestamp: 1707045571 Timestamp [UCT]: 2024-02-04 11:19:31 Age [y:d:h:m:s]: 01:275:14:57:39
Block: 950144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455750 RingCT/type: yes/0
Extra: 01399c091a5f850afc13740303f2f14ebeef2ddd4db3e95a4c9d0041c7dfd0049d02110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66a1ddf20d4247021b0ccc6d9f4d0c15af2c866458b8b4b50a137f76ea93c603 0.600000000000 1408708 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": 950154, "vin": [ { "gen": { "height": 950144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66a1ddf20d4247021b0ccc6d9f4d0c15af2c866458b8b4b50a137f76ea93c603" } } ], "extra": [ 1, 57, 156, 9, 26, 95, 133, 10, 252, 19, 116, 3, 3, 242, 241, 78, 190, 239, 45, 221, 77, 179, 233, 90, 76, 157, 0, 65, 199, 223, 208, 4, 157, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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