Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f6379a537d008a08926d22005c1b5c6cb19c168fd69f9e9585f02c72e246f16

Tx prefix hash: 30b12c2ab83f36bff1e7bc0a93570318f77ec5c1d5326390bbadb438c5cd23f1
Tx public key: 1d16a8e912617a75a28fd45e4c55c39eef411c8eef322ad51be5ff96a69c3dc4
Timestamp: 1677598332 Timestamp [UCT]: 2023-02-28 15:32:12 Age [y:d:h:m:s]: 01:362:15:46:13
Block: 706910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519864 RingCT/type: yes/0
Extra: 011d16a8e912617a75a28fd45e4c55c39eef411c8eef322ad51be5ff96a69c3dc4021100000001835e4d22000000000000000000

1 output(s) for total of 2.790703010000 dcy

stealth address amount amount idx
00: f212f1bee69cfef08d6539d41c2a07a4d8c3a899781e48e82a3663722f834cb8 2.790703010000 1150695 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": 706920, "vin": [ { "gen": { "height": 706910 } } ], "vout": [ { "amount": 2790703010, "target": { "key": "f212f1bee69cfef08d6539d41c2a07a4d8c3a899781e48e82a3663722f834cb8" } } ], "extra": [ 1, 29, 22, 168, 233, 18, 97, 122, 117, 162, 143, 212, 94, 76, 85, 195, 158, 239, 65, 28, 142, 239, 50, 42, 213, 27, 229, 255, 150, 166, 156, 61, 196, 2, 17, 0, 0, 0, 1, 131, 94, 77, 34, 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