Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b08b2ae4662c8a1e73b2e1b26190c48b782866f6797e1d54b6cc5829c0b246

Tx prefix hash: 546f99d81fb790958723d0a82a37a92637cdee72e45bbfaabd1dca70e2cf568d
Tx public key: 8ae660900364f19d66c97b47494a11603cea048c7f86bb24c6c127a5632f1528
Timestamp: 1576424389 Timestamp [UCT]: 2019-12-15 15:39:49 Age [y:d:h:m:s]: 04:341:12:59:53
Block: 27342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130240 RingCT/type: yes/0
Extra: 018ae660900364f19d66c97b47494a11603cea048c7f86bb24c6c127a5632f1528021100000023ad433a0b000000000000000000

1 output(s) for total of 498.202003813000 dcy

stealth address amount amount idx
00: cd6d17f40f48b2f4b316d90651829ad6158fbdca6d0179c9573f16cdf22f0317 498.202003813000 45338 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": 27352, "vin": [ { "gen": { "height": 27342 } } ], "vout": [ { "amount": 498202003813, "target": { "key": "cd6d17f40f48b2f4b316d90651829ad6158fbdca6d0179c9573f16cdf22f0317" } } ], "extra": [ 1, 138, 230, 96, 144, 3, 100, 241, 157, 102, 201, 123, 71, 73, 74, 17, 96, 60, 234, 4, 140, 127, 134, 187, 36, 198, 193, 39, 165, 99, 47, 21, 40, 2, 17, 0, 0, 0, 35, 173, 67, 58, 11, 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