Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bd13e94d7b4c34bb653bbe4494eb38d71d31f6bedc1e9e9b7c22bf8220744a9

Tx prefix hash: 25fdd38a7e66c3dbdf6681ed3cd4fff4ad276f87d7a6a2f156ae0c92cfe45cc7
Tx public key: 7010e82a28c88b870715403b29229caeb1f97c255d097044ab9f055f46a9f57b
Timestamp: 1692314729 Timestamp [UCT]: 2023-08-17 23:25:29 Age [y:d:h:m:s]: 01:152:12:46:12
Block: 828195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370392 RingCT/type: yes/0
Extra: 017010e82a28c88b870715403b29229caeb1f97c255d097044ab9f055f46a9f57b02110000001833af99f4000000000000000000

1 output(s) for total of 1.106232093000 dcy

stealth address amount amount idx
00: 49edb80e38e9efe7f84cdbf1c5d9fe71e401c3303db8171e952c92553e37ee8b 1.106232093000 1280515 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": 828205, "vin": [ { "gen": { "height": 828195 } } ], "vout": [ { "amount": 1106232093, "target": { "key": "49edb80e38e9efe7f84cdbf1c5d9fe71e401c3303db8171e952c92553e37ee8b" } } ], "extra": [ 1, 112, 16, 232, 42, 40, 200, 139, 135, 7, 21, 64, 59, 41, 34, 156, 174, 177, 249, 124, 37, 93, 9, 112, 68, 171, 159, 5, 95, 70, 169, 245, 123, 2, 17, 0, 0, 0, 24, 51, 175, 153, 244, 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