Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fcb3ca848f85828148f0ac188fd5d6ad80d1abb9677f23b3dc9fc120cc43298

Tx prefix hash: b8bf42c65de890279f92478e5f4985dee745f0282d5df27d79ecd94b3b9e975c
Tx public key: e35316f883eaae582693728da456b6fd63cd7ea3fe2ee4a38ab78993242f5516
Timestamp: 1631688247 Timestamp [UCT]: 2021-09-15 06:44:07 Age [y:d:h:m:s]: 03:051:21:36:33
Block: 334160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 812677 RingCT/type: yes/0
Extra: 01e35316f883eaae582693728da456b6fd63cd7ea3fe2ee4a38ab78993242f551602110000006f5410958b000000000000000000

1 output(s) for total of 47.950114000000 dcy

stealth address amount amount idx
00: 018cb2de4ead8df14fce4a589eb95dc01d13272b508f5faae3eef5e588e0976c 47.950114000000 689339 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": 334170, "vin": [ { "gen": { "height": 334160 } } ], "vout": [ { "amount": 47950114000, "target": { "key": "018cb2de4ead8df14fce4a589eb95dc01d13272b508f5faae3eef5e588e0976c" } } ], "extra": [ 1, 227, 83, 22, 248, 131, 234, 174, 88, 38, 147, 114, 141, 164, 86, 182, 253, 99, 205, 126, 163, 254, 46, 228, 163, 138, 183, 137, 147, 36, 47, 85, 22, 2, 17, 0, 0, 0, 111, 84, 16, 149, 139, 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