Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbc54781ee5a45196659679bd46449f67d5d93508a2888b6ecf7c69c2767289c

Tx prefix hash: 03776b614d5354b197029e2040e1c415e7acb7c83893793fe11a9821bef76774
Tx public key: d4b489b9078eb4df85d5be8878f43f4d47a4809db3c181dabfc6b5d44fa6598f
Timestamp: 1709328636 Timestamp [UCT]: 2024-03-01 21:30:36 Age [y:d:h:m:s]: 01:258:02:35:06
Block: 969089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443200 RingCT/type: yes/0
Extra: 01d4b489b9078eb4df85d5be8878f43f4d47a4809db3c181dabfc6b5d44fa6598f02110000000f7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d41da4d67c82638c217c96e82f464cd6ea0df3eaa337eb961f4346e6bfa575 0.600000000000 1428916 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": 969099, "vin": [ { "gen": { "height": 969089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d41da4d67c82638c217c96e82f464cd6ea0df3eaa337eb961f4346e6bfa575" } } ], "extra": [ 1, 212, 180, 137, 185, 7, 142, 180, 223, 133, 213, 190, 136, 120, 244, 63, 77, 71, 164, 128, 157, 179, 193, 129, 218, 191, 198, 181, 212, 79, 166, 89, 143, 2, 17, 0, 0, 0, 15, 122, 156, 244, 199, 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