Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffd52e8e985d38f090059cd26f5aebb733fd99325717242685469fb5c83ae32d

Tx prefix hash: 06dbad2d544edad653e45dc4130ac4dae21beb1e62e3098c278cb7e6f92033c2
Tx public key: 2a347cde46289425e7c91b328444a18ba41fe87d2c0a7c5c6895608a38310940
Timestamp: 1638490912 Timestamp [UCT]: 2021-12-03 00:21:52 Age [y:d:h:m:s]: 03:161:11:56:53
Block: 387141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 894160 RingCT/type: yes/0
Extra: 012a347cde46289425e7c91b328444a18ba41fe87d2c0a7c5c6895608a3831094002110000000306faf294000000000000000000

1 output(s) for total of 32.006746296000 dcy

stealth address amount amount idx
00: e707b16f072a9cdb790c4e17d1c91408dc61a44d9fa5c8aed60c6763a4666e7a 32.006746296000 780898 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": 387151, "vin": [ { "gen": { "height": 387141 } } ], "vout": [ { "amount": 32006746296, "target": { "key": "e707b16f072a9cdb790c4e17d1c91408dc61a44d9fa5c8aed60c6763a4666e7a" } } ], "extra": [ 1, 42, 52, 124, 222, 70, 40, 148, 37, 231, 201, 27, 50, 132, 68, 161, 139, 164, 31, 232, 125, 44, 10, 124, 92, 104, 149, 96, 138, 56, 49, 9, 64, 2, 17, 0, 0, 0, 3, 6, 250, 242, 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