Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b3158796c6df09c3bd96e53bca39cf75d98444a6674717eeb282fb9344e18f

Tx prefix hash: 24e23b3133a608818fb7605775dcd0a24c796295c151f5bb444151e3f52f577d
Tx public key: a8e4067a1abc8abcd0dfa7865fe7aea815e887df4d28f3b8b49a7e8351a7fd49
Timestamp: 1714236104 Timestamp [UCT]: 2024-04-27 16:41:44 Age [y:d:h:m:s]: 01:186:08:27:35
Block: 1009758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391840 RingCT/type: yes/0
Extra: 01a8e4067a1abc8abcd0dfa7865fe7aea815e887df4d28f3b8b49a7e8351a7fd4902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aed7bcf949c5bebc3d562df1a5b2a2610d554a90fb2e07c9b5e4bc69465331ab 0.600000000000 1471522 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": 1009768, "vin": [ { "gen": { "height": 1009758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aed7bcf949c5bebc3d562df1a5b2a2610d554a90fb2e07c9b5e4bc69465331ab" } } ], "extra": [ 1, 168, 228, 6, 122, 26, 188, 138, 188, 208, 223, 167, 134, 95, 231, 174, 168, 21, 232, 135, 223, 77, 40, 243, 184, 180, 154, 126, 131, 81, 167, 253, 73, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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