Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f6184481d4ef7dbe6d5cb057b4a115d908d5e8bf7af8df8d1aaf524b586c7d

Tx prefix hash: f3757716b34deb2b1e671ae74b529f7c8820a5ec5326c1875307fbec40ae4d42
Tx public key: fa35cb0e55d6b5943b3b6300b381d5063f9f08d964cd65e0d8850f41f8d5f46d
Timestamp: 1705845332 Timestamp [UCT]: 2024-01-21 13:55:32 Age [y:d:h:m:s]: 01:315:11:08:50
Block: 940170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484320 RingCT/type: yes/0
Extra: 01fa35cb0e55d6b5943b3b6300b381d5063f9f08d964cd65e0d8850f41f8d5f46d02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8943dfffb379ef497fd68af99c45a3fbf392d948e0c48a45f420ff7fd121c98 0.600000000000 1398304 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": 940180, "vin": [ { "gen": { "height": 940170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8943dfffb379ef497fd68af99c45a3fbf392d948e0c48a45f420ff7fd121c98" } } ], "extra": [ 1, 250, 53, 203, 14, 85, 214, 181, 148, 59, 59, 99, 0, 179, 129, 213, 6, 63, 159, 8, 217, 100, 205, 101, 224, 216, 133, 15, 65, 248, 213, 244, 109, 2, 17, 0, 0, 0, 6, 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